Content Collections

**Referenced Files in This Document** - [config.yml](file://src/admin/config.yml) - [cases.11tydata.json](file://src/content/cases/cases.11tydata.json) - [news.11tydata.json](file://src/content/news/news.11tydata.json) - [team.11tydata.json](file://src/content/team/team.11tydata.json) - [knowledge.11tydata.js](file://src/content/knowledge/knowledge.11tydata.js) - [newsletters.11tydata.json](file://src/content/newsletters/newsletters.11tydata.json) - [adelaide-city-fc.md](file://src/content/cases/adelaide-city-fc.md) - [2025-10-17-political-powerhouse.md](file://src/content/news/2025-10-17-political-powerhouse.md) - [01-matt-neagle.md](file://src/content/team/01-matt-neagle.md) - [briefing-note-playbook.md](file://src/content/knowledge/briefing-note-playbook.md) - [media-enquiry-protocol.md](file://src/content/knowledge/media-enquiry-protocol.md) - [staff-onboarding.md](file://src/content/knowledge/staff-onboarding.md) - [diarkis.md](file://src/content/cases/diarkis.md) - [curabitur-ullamcorper-ultricies-nisi.md](file://src/content/newsletters/curabitur-ullamcorper-ultricies-nisi.md) - [case-study-card.njk](file://src/_includes/macros/case-study-card.njk) - [news-article-card.njk](file://src/_includes/macros/news-article-card.njk) - [team-flip-card.njk](file://src/_includes/macros/team-flip-card.njk) - [testimonial-card.njk](file://src/_includes/macros/testimonial-card.njk) - [knowledge.njk](file://src/_includes/layouts/knowledge.njk)

Update Summary

Changes Made

  • Added documentation for three new staff knowledge base articles: Briefing Note Playbook, Media Enquiry Protocol, and Staff Onboarding guide
  • Updated Matt Neagle's team member profile with expanded biography and role change to 'Founder & Managing Director'
  • Added new Diarkis case study with updated content and testimonials
  • Enhanced Knowledge Base documentation with comprehensive frontmatter schema including status, categories, content types, and audience fields

Table of Contents

  1. Introduction
  2. Project Structure
  3. Core Components
  4. Architecture Overview
  5. Detailed Component Analysis
  6. Dependency Analysis
  7. Performance Considerations
  8. Troubleshooting Guide
  9. Conclusion
  10. Appendices

Introduction

This document describes all content collections in the Ace Strategies Prime platform, including their frontmatter schemas, processing rules, templates, and publishing workflows. It covers:

  • News & Insights with rich text editing and media support
  • Case Studies with client testimonials and categorization
  • Team Member profiles with biographical information and images
  • Knowledge Base articles with Obsidian integration and comprehensive metadata
  • Newsletter archives

It also explains how content is interconnected, how the CMS integrates with static site generation, and provides best practices for content creators.

Project Structure

The platform organizes content collections under src/content with per-collection Eleventy configuration and Nunjucks templates. The Netlify CMS configuration (config.yml) defines editable fields and media handling for each collection.

graph TB
CMS["Netlify CMS Config<br/>src/admin/config.yml"] --> Collections["Collections"]
Collections --> News["News & Insights<br/>src/content/news/*.md"]
Collections --> Cases["Case Studies<br/>src/content/cases/*.md"]
Collections --> Team["Team Members<br/>src/content/team/*.md"]
Collections --> Knowledge["Knowledge Base<br/>src/content/knowledge/*.md"]
Collections --> Newsletters["Newsletter Archives<br/>src/content/newsletters/*.md"]
News --> NewsData[".11tydata.json<br/>news.11tydata.json"]
Cases --> CasesData[".11tydata.json<br/>cases.11tydata.json"]
Team --> TeamData[".11tydata.json<br/>team.11tydata.json"]
Knowledge --> KnowledgeData[".11tydata.js<br/>knowledge.11tydata.js"]
Newsletters --> NewslettersData[".11tydata.json<br/>newsletters.11tydata.json"]
Templates["Nunjucks Macros & Layouts"] --> Views["Views & Pages"]
Templates --> NewsCards["news-article-card.njk"]
Templates --> CaseCards["case-study-card.njk"]
Templates --> TeamCards["team-flip-card.njk"]
Templates --> TestimonialCard["testimonial-card.njk"]
Templates --> KnowledgeLayout["knowledge.njk"]
NewsData --> Views
CasesData --> Views
TeamData --> Views
KnowledgeData --> Views
NewslettersData --> Views

Diagram sources

  • [config.yml:11-105](file://src/admin/config.yml#L11-L105)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)
  • [news-article-card.njk:1-35](file://src/_includes/macros/news-article-card.njk#L1-L35)
  • [case-study-card.njk:1-20](file://src/_includes/macros/case-study-card.njk#L1-L20)
  • [team-flip-card.njk:1-18](file://src/_includes/macros/team-flip-card.njk#L1-L18)
  • [testimonial-card.njk:1-18](file://src/_includes/macros/testimonial-card.njk#L1-L18)
  • [knowledge.njk:1-43](file://src/_includes/layouts/knowledge.njk#L1-L43)

Section sources

  • [config.yml:11-105](file://src/admin/config.yml#L11-L105)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Core Components

This section documents each collection's purpose, frontmatter fields, and processing behavior.

  • News & Insights

    • Purpose: Announcements, press releases, and insights with optional PDF downloads and excerpts.
    • CMS fields: title, date, author, excerpt, image, image_alt, pdf_url, pdf_label, featured, draft, body (markdown).
    • Processing: Permalink disabled; rendered via templates that show excerpts and optional expanded content.
    • Example frontmatter: [2025-10-17-political-powerhouse.md:1-11](file://src/content/news/2025-10-17-political-powerhouse.md#L1-L11)
    • Template usage: [news-article-card.njk:1-35](file://src/_includes/macros/news-article-card.njk#L1-L35)

  • Case Studies

    • Purpose: Client outcomes with testimonials, categorized by service area.
    • CMS fields: client, category (select), engagement title, image, image_alt, client quote, quote author, display order, featured, draft, body (markdown).
    • Processing: Permalink disabled; testimonials are rendered via a dedicated macro.
    • Example frontmatter: [adelaide-city-fc.md:1-11](file://src/content/cases/adelaide-city-fc.md#L1-L11)
    • Template usage: [case-study-card.njk:1-20](file://src/_includes/macros/case-study-card.njk#L1-L20)

  • Team Members

    • Purpose: Profiles with homepage and profile page images, short bios, and ordering.
    • CMS fields: anchor, full name, role/title, display order, homepage card image, profile page image, alt texts, short bio, featured, draft, full bio (markdown).
    • Processing: Permalink disabled; homepage cards flip to reveal short bio.
    • Example frontmatter: [01-matt-neagle.md:1-12](file://src/content/team/01-matt-neagle.md#L1-L12)
    • Template usage: [team-flip-card.njk:1-18](file://src/_includes/macros/team-flip-card.njk#L1-L18)

  • Knowledge Base

    • Purpose: Obsidian-integrated articles published automatically on commit with comprehensive metadata and status management.
    • CMS fields: status (select: draft, review, published, archived), title, date, last_updated, author, reviewer, excerpt, category (select), subcategory, tags_list (list), content_type (select), difficulty (select), featured_image, image_alt, audience (select: both, staff, members), seo_description, noindex, related_articles (list with title and url), featured, table_of_contents, order, body (markdown).
    • Processing: Custom layout and permalink computed to a members' knowledge route; tagged as "knowledge"; status-based visibility control.
    • Example frontmatter: [briefing-note-playbook.md:1-30](file://src/content/knowledge/briefing-note-playbook.md#L1-L30)
    • Template usage: [knowledge.njk:1-43](file://src/_includes/layouts/knowledge.njk#L1-L43)

  • Newsletter Archives

    • Purpose: Newsletter issues with optional PDF and archive links.
    • CMS fields: title, date, excerpt, PDF link, archive link, featured, draft.
    • Processing: Permalink disabled; tagged as "newsletters".
    • Example frontmatter: [curabitur-ullamcorper-ultricies-nisi.md:1-9](file://src/content/newsletters/curabitur-ullamcorper-ultricies-nisi.md#L1-L9)

Validation and defaults observed in CMS config:

  • Boolean fields default to false unless otherwise specified.
  • Some fields are marked required in the CMS schema; others are optional.

Section sources

  • [config.yml:15-31](file://src/admin/config.yml#L15-L31)
  • [config.yml:33-58](file://src/admin/config.yml#L33-L58)
  • [config.yml:60-77](file://src/admin/config.yml#L60-L77)
  • [config.yml:79-90](file://src/admin/config.yml#L79-L90)
  • [config.yml:92-104](file://src/admin/config.yml#L92-L104)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Architecture Overview

The CMS writes content to the repository; Eleventy reads frontmatter and content, applies computed permalinks and tags, and renders views using Nunjucks macros and layouts.

sequenceDiagram
participant Author as "Content Author"
participant CMS as "Netlify CMS"
participant Repo as "Repository"
participant Eleventy as "Eleventy Build"
participant Views as "Rendered Views"
Author->>CMS : "Edit/create collection item"
CMS->>Repo : "Commit YAML frontmatter + markdown"
Repo-->>Eleventy : "Files in src/content/*"
Eleventy->>Eleventy : "Apply .11tydata transforms"
Eleventy->>Views : "Render via Nunjucks macros/layouts"
Views-->>Author : "Published pages"

Diagram sources

  • [config.yml:11-105](file://src/admin/config.yml#L11-L105)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)
  • [news-article-card.njk:1-35](file://src/_includes/macros/news-article-card.njk#L1-L35)
  • [case-study-card.njk:1-20](file://src/_includes/macros/case-study-card.njk#L1-L20)
  • [team-flip-card.njk:1-18](file://src/_includes/macros/team-flip-card.njk#L1-L18)
  • [knowledge.njk:1-43](file://src/_includes/layouts/knowledge.njk#L1-L43)

Detailed Component Analysis

News & Insights

  • Frontmatter fields
    • Required: title, date
    • Optional: author, excerpt, image, image_alt, pdf_url, pdf_label, featured, draft, body
  • Validation rules
    • Boolean defaults: draft defaults to false if unspecified
    • Image and PDF fields are optional; PDF link and label often appear together
  • Publishing workflow
    • Create/edit via CMS; set draft=false to publish; commit to trigger build
  • Interconnections
    • Homepage and news pages consume excerpts and dates; optional expanded content shown in detail view
  • Practical example
    • See [2025-10-17-political-powerhouse.md](file://src/content/news/2025-10-17-political-powerhouse.md)
flowchart TD
Start(["Create/Edit News Item"]) --> Fill["Fill frontmatter fields"]
Fill --> Review["Review: required fields present"]
Review --> |Missing required| Fix["Add missing fields"]
Review --> |Complete| Publish["Set draft=false"]
Publish --> Commit["Commit to repository"]
Commit --> Build["Eleventy build"]
Build --> Render["Render via news-article-card.njk"]
Render --> PublishLive["Publish live page"]

Diagram sources

  • [config.yml:20-31](file://src/admin/config.yml#L20-L31)
  • [news-article-card.njk:1-35](file://src/_includes/macros/news-article-card.njk#L1-L35)

Section sources

  • [config.yml:15-31](file://src/admin/config.yml#L15-L31)
  • [2025-10-17-political-powerhouse.md:1-11](file://src/content/news/2025-10-17-political-powerhouse.md#L1-L11)
  • [news-article-card.njk:1-35](file://src/_includes/macros/news-article-card.njk#L1-L35)

Case Studies

  • Frontmatter fields
    • Required: client
    • Optional: category (select), title, image, image_alt, quote, quote_author, order, featured, draft, body
  • Validation rules
    • Category is a select with predefined options
    • Draft defaults to false if unspecified
  • Publishing workflow
    • Add testimonials; set draft=false; commit; build renders cards and quote boxes
  • Interconnections
    • Testimonials are rendered via [testimonial-card.njk](file://src/_includes/macros/testimonial-card.njk) and embedded in case study cards
sequenceDiagram
participant CMS as "CMS"
participant Repo as "Repository"
participant Eleventy as "Eleventy"
participant Macro as "case-study-card.njk"
CMS->>Repo : "Save case study frontmatter + body"
Repo-->>Eleventy : "cases/*.md"
Eleventy->>Macro : "Render with item.data + item.content"
Macro-->>Eleventy : "HTML with quote box"
Eleventy-->>CMS : "Published page"

Diagram sources

  • [config.yml:38-58](file://src/admin/config.yml#L38-L58)
  • [case-study-card.njk:1-20](file://src/_includes/macros/case-study-card.njk#L1-L20)
  • [testimonial-card.njk:1-18](file://src/_includes/macros/testimonial-card.njk#L1-L18)

Section sources

  • [config.yml:33-58](file://src/admin/config.yml#L33-L58)
  • [adelaide-city-fc.md:1-11](file://src/content/cases/adelaide-city-fc.md#L1-L11)
  • [case-study-card.njk:1-20](file://src/_includes/macros/case-study-card.njk#L1-L20)
  • [testimonial-card.njk:1-18](file://src/_includes/macros/testimonial-card.njk#L1-L18)

Team Members

  • Frontmatter fields
    • Required: anchor, name
    • Optional: role, order, image_index, image_profile, image_alt_index, image_alt_profile, bio_short, featured, draft, body
  • Validation rules
    • Draft defaults to false if unspecified
    • Homepage and profile images are optional; alt texts recommended
  • Publishing workflow
    • Set order for homepage grid; set draft=false; commit; build renders flip cards
  • Interconnections
    • Homepage teaser uses flip cards; profile pages link via anchor
flowchart TD
Start(["Create/Edit Team Member"]) --> Fields["Enter required + optional fields"]
Fields --> DraftCheck{"Draft?"}
DraftCheck --> |Yes| SaveDraft["Keep draft=true"]
DraftCheck --> |No| Publish["Set draft=false"]
Publish --> Commit["Commit to repository"]
Commit --> Build["Eleventy build"]
Build --> Flip["Render via team-flip-card.njk"]
Flip --> PublishLive["Publish live profile"]

Diagram sources

  • [config.yml:64-77](file://src/admin/config.yml#L64-L77)
  • [team-flip-card.njk:1-18](file://src/_includes/macros/team-flip-card.njk#L1-L18)

Section sources

  • [config.yml:60-77](file://src/admin/config.yml#L60-L77)
  • [01-matt-neagle.md:1-12](file://src/content/team/01-matt-neagle.md#L1-L12)
  • [team-flip-card.njk:1-18](file://src/_includes/macros/team-flip-card.njk#L1-L18)

Knowledge Base

  • Frontmatter fields
    • Required: status (select: draft, review, published, archived), title
    • Optional: date, last_updated, author, reviewer, excerpt, category (select), subcategory, tags_list, content_type (select), difficulty (select), featured_image, image_alt, audience (select: both, staff, members), seo_description, noindex, related_articles, featured, table_of_contents, order, body
  • Processing rules
    • Uses custom layout [knowledge.njk](file://src/_includes/layouts/knowledge.njk)
    • Computed permalink: members' knowledge article path
    • Tagged as "knowledge"
    • Status-based visibility control: production builds exclude non-published content from collections
  • Obsidian integration
    • Notes are authored in Obsidian and committed to src/content/knowledge; automatic publishing on push
  • Publishing workflow
    • Write in Obsidian; commit; build publishes to computed permalink
  • Updated Enhanced with comprehensive metadata including status management, categories, content types, difficulty levels, audience targeting, and related articles
sequenceDiagram
participant Author as "Obsidian Author"
participant Repo as "Repository"
participant Eleventy as "Eleventy"
participant Layout as "knowledge.njk"
Author->>Repo : "Commit knowledge/*.md"
Repo-->>Eleventy : "Source files"
Eleventy->>Eleventy : "Apply knowledge.11tydata.js"
Eleventy->>Layout : "Render with computed permalink"
Layout-->>Author : "Published knowledge article"

Diagram sources

  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [knowledge.njk:1-43](file://src/_includes/layouts/knowledge.njk#L1-L43)

Section sources

  • [config.yml:79-90](file://src/admin/config.yml#L79-L90)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [briefing-note-playbook.md:1-30](file://src/content/knowledge/briefing-note-playbook.md#L1-L30)
  • [media-enquiry-protocol.md:1-30](file://src/content/knowledge/media-enquiry-protocol.md#L1-L30)
  • [staff-onboarding.md:1-30](file://src/content/knowledge/staff-onboarding.md#L1-L30)
  • [knowledge.njk:1-43](file://src/_includes/layouts/knowledge.njk#L1-L43)

Newsletter Archives

  • Frontmatter fields
    • Required: title, date
    • Optional: excerpt, pdf_link, archive_link, featured, draft
  • Processing rules
    • Permalink disabled; tagged as "newsletters"
  • Publishing workflow
    • Set draft=false; commit; build renders archive entries

Section sources

  • [config.yml:92-104](file://src/admin/config.yml#L92-L104)
  • [curabitur-ullamcorper-ultricies-nisi.md:1-9](file://src/content/newsletters/curabitur-ullamcorper-ultricies-nisi.md#L1-L9)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Dependency Analysis

  • CMS-to-Eleventy coupling
    • CMS field definitions drive the shape of frontmatter; Eleventy's .11tydata files transform content and compute permalinks
  • Template coupling
    • Macros depend on specific frontmatter keys (e.g., image, excerpt, quote)
  • Tagging and routing
    • Knowledge and newsletters collections use tags and computed permalinks to control routing and discovery
graph LR
CMSConfig["CMS Config<br/>config.yml"] --> NewsFM["News Frontmatter"]
CMSConfig --> CasesFM["Cases Frontmatter"]
CMSConfig --> TeamFM["Team Frontmatter"]
CMSConfig --> KnowledgeFM["Knowledge Frontmatter"]
CMSConfig --> NewslettersFM["Newsletters Frontmatter"]
NewsData["news.11tydata.json"] --> NewsView["News View"]
CasesData["cases.11tydata.json"] --> CasesView["Cases View"]
TeamData["team.11tydata.json"] --> TeamView["Team View"]
KnowledgeData["knowledge.11tydata.js"] --> KnowledgeView["Knowledge View"]
NewslettersData["newsletters.11tydata.json"] --> NewslettersView["Newsletters View"]
NewsFM --> NewsView
CasesFM --> CasesView
TeamFM --> TeamView
KnowledgeFM --> KnowledgeView
NewslettersFM --> NewslettersView

Diagram sources

  • [config.yml:11-105](file://src/admin/config.yml#L11-L105)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Section sources

  • [config.yml:11-105](file://src/admin/config.yml#L11-L105)
  • [news.11tydata.json:1-2](file://src/content/news/news.11tydata.json#L1-L2)
  • [cases.11tydata.json:1-2](file://src/content/cases/cases.11tydata.json#L1-L2)
  • [team.11tydata.json:1-2](file://src/content/team/team.11tydata.json#L1-L2)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Performance Considerations

  • Prefer lazy-loading images in templates to reduce initial payload.
  • Limit large PDF attachments; link externally when possible.
  • Use excerpts to keep lists and carousels lightweight.
  • Keep Knowledge Base notes concise; rely on internal linking for depth.
  • Avoid unnecessary computed permalinks for frequently changing content.

Troubleshooting Guide

  • Missing required fields
    • Symptoms: Build errors or missing metadata in views
    • Resolution: Ensure required fields are present per collection schema
  • Draft not publishing
    • Symptoms: Content remains hidden
    • Resolution: Set draft=false and commit
  • Incorrect image rendering
    • Symptoms: Broken images or missing alt text
    • Resolution: Verify image paths and alt fields; ensure images are uploaded via CMS media folder
  • Knowledge article not appearing
    • Symptoms: Missing from members' knowledge section
    • Resolution: Confirm computed permalink and "knowledge" tag in .11tydata; ensure commit triggered build
  • Newsletter not tagged
    • Symptoms: Missing from newsletters routes
    • Resolution: Confirm "newsletters" tag in .11tydata

Section sources

  • [config.yml:20-31](file://src/admin/config.yml#L20-L31)
  • [config.yml:38-58](file://src/admin/config.yml#L38-L58)
  • [config.yml:64-77](file://src/admin/config.yml#L64-L77)
  • [config.yml:79-90](file://src/admin/config.yml#L79-L90)
  • [config.yml:92-104](file://src/admin/config.yml#L92-L104)
  • [knowledge.11tydata.js:1-8](file://src/content/knowledge/knowledge.11tydata.js#L1-L8)
  • [newsletters.11tydata.json:1-2](file://src/content/newsletters/newsletters.11tydata.json#L1-L2)

Conclusion

The Ace Strategies Prime platform uses Netlify CMS to manage structured content and Eleventy to transform and render it into optimized pages. Each collection has a defined frontmatter schema, processing rules, and templates. Following the documented workflows and best practices ensures reliable publishing and maintainable content.

Appendices

Frontmatter Field Reference

  • News & Insights
    • title (required), date (required), author (optional), excerpt (optional), image (optional), image_alt (optional), pdf_url (optional), pdf_label (optional), featured (optional), draft (optional, default false), body (required)
  • Case Studies
    • client (required), category (optional), title (optional), image (optional), image_alt (optional), quote (optional), quote_author (optional), order (optional), featured (optional), draft (optional, default false), body (required)
  • Team Members
    • anchor (required), name (required), role (optional), order (optional), image_index (optional), image_profile (optional), image_alt_index (optional), image_alt_profile (optional), bio_short (optional), featured (optional), draft (optional, default false), body (required)
  • Knowledge Base
    • status (required, select: draft, review, published, archived), title (required), date (optional), last_updated (optional), author (optional), reviewer (optional), excerpt (optional), category (optional), subcategory (optional), tags_list (optional), content_type (optional), difficulty (optional), featured_image (optional), image_alt (optional), audience (optional, select: both, staff, members), seo_description (optional), noindex (optional), related_articles (optional), featured (optional), table_of_contents (optional), order (optional), body (required)
  • Newsletter Archives
    • title (required), date (required), excerpt (optional), pdf_link (optional), archive_link (optional), featured (optional), draft (optional, default false)

Section sources

  • [config.yml:15-31](file://src/admin/config.yml#L15-L31)
  • [config.yml:33-58](file://src/admin/config.yml#L33-L58)
  • [config.yml:60-77](file://src/admin/config.yml#L60-L77)
  • [config.yml:79-90](file://src/admin/config.yml#L79-L90)
  • [config.yml:92-104](file://src/admin/config.yml#L92-L104)

New Knowledge Base Articles

Updated Added comprehensive documentation for three new staff knowledge base articles:

Briefing Note Playbook

  • Purpose: House standard for producing briefing notes from commissioning through to sign-off
  • Status: published
  • Category: Practice Playbooks
  • Audience: staff
  • Content Type: How-To Guide
  • Difficulty: Intermediate
  • Related Articles: Style Guide, Content Templates & Examples, Media Enquiry Protocol, Review & Publish Workflow

Media Enquiry Protocol

  • Purpose: Fast-path protocol for triaging, logging, drafting, and clearing media responses
  • Status: published
  • Category: Practice Playbooks
  • Audience: staff
  • Content Type: How-To Guide
  • Difficulty: Intermediate
  • Related Articles: Briefing Note Playbook, Style Guide, Staff Onboarding, Review & Publish Workflow

Staff Onboarding Guide

  • Purpose: First two weeks at Ace Strategies including accounts setup, documents, and house rules
  • Status: published
  • Category: Onboarding
  • Audience: staff
  • Content Type: How-To Guide
  • Difficulty: Beginner
  • Related Articles: Quick Start Guide, Style Guide, Briefing Note Playbook, Media Enquiry Protocol, Glossary

Section sources

  • [briefing-note-playbook.md:1-30](file://src/content/knowledge/briefing-note-playbook.md#L1-L30)
  • [media-enquiry-protocol.md:1-30](file://src/content/knowledge/media-enquiry-protocol.md#L1-L30)
  • [staff-onboarding.md:1-30](file://src/content/knowledge/staff-onboarding.md#L1-L30)

Updated Team Member Profile

Updated Matt Neagle's profile now includes:

  • Role: Founder & Managing Director
  • Expanded biography highlighting extensive expertise in government relations, strategic communications, and media management
  • Professional background including roles advising across political portfolios and strategic positions in critical national security projects
  • Founding member of Invest Australia Alliance

Section sources

  • [01-matt-neagle.md:1-19](file://src/content/team/01-matt-neagle.md#L1-L19)

New Case Study

Updated Added Diarkis case study featuring:

  • Client: Diarkis (next-generation Command and Control systems)
  • Category: Strategic Communications
  • Testimonial from Nobuyori Takahashi, Founder/CEO
  • Focus on market entry into Australia and growth across defense and civilian sectors

Section sources

  • [diarkis.md:1-14](file://src/content/cases/diarkis.md#L1-L14)